Skip to content

[RelEng] Migrate repo.eclipse.org links to new Nexus3 schema#3719

Merged
HannesWell merged 1 commit into
eclipse-platform:masterfrom
HannesWell:fix-eclipse.repo-links
Mar 19, 2026
Merged

[RelEng] Migrate repo.eclipse.org links to new Nexus3 schema#3719
HannesWell merged 1 commit into
eclipse-platform:masterfrom
HannesWell:fix-eclipse.repo-links

Conversation

@HannesWell

@HannesWell HannesWell commented Mar 19, 2026

Copy link
Copy Markdown
Member

Replace the last path segment in repo.eclipse.org URL using the following rules (with the project's short name):

  • <short_name>-snapshots -> <short_name>-maven2-snapshots
  • <short_name>-releases -> <short_name>-maven2-releases
  • <short_name> -> <short_name>-maven2

Following the announcement at

This will hopefully fix the failure in deploying the parent-pom and sdk target to the eclipse maven snapshot repository.

In general the links in all submodules could be updated too, but atm. it seems like the redirects from the old schema still work.

Replace the last path segment in repo.eclipse.org URL using the
following rules (with the project's short name):
- <short_name>-snapshots -> <short_name>-maven2-snapshots
- <short_name>-releases -> <short_name>-maven2-releases
- <short_name> -> <short_name>-maven2
@HannesWell

Copy link
Copy Markdown
Member Author

This will hopefully fix the failure in deploying the parent-pom and sdk target to the eclipse maven snapshot repository.

The deployment on the master still fails, but e.g. the deployment to Maven still works even with the old URLs.
Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

@HannesWell

Copy link
Copy Markdown
Member Author

Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

Asked the IT team for help:
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

@HannesWell HannesWell merged commit 234ebc6 into eclipse-platform:master Mar 19, 2026
6 checks passed
@HannesWell HannesWell deleted the fix-eclipse.repo-links branch March 19, 2026 19:14
@HannesWell

Copy link
Copy Markdown
Member Author

Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

Asked the IT team for help: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

That fixed it. The parent-pom and sdk-target are now deployed again as desired.

@HannesWell

Copy link
Copy Markdown
Member Author

Asked the IT team for help: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

That fixed it. The parent-pom and sdk-target are now deployed again as desired.

At the same time the deployment to Maven failed again now.
Reopened the help-desk issue and asked for help again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant